Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python requirements: bump protobuf version to match 7494535 #37683

Closed
wants to merge 1 commit into from

Conversation

efd6
Copy link
Contributor

@efd6 efd6 commented Jan 21, 2024

Proposed commit message

The change in 7494535 did not update these requirements, resulting in inconsistent requirements and doc check failure:

ERROR: Cannot install protobuf==3.19.4 and protobuf==3.19.5 because these package versions have conflicting dependencies.

ref:https://github.com/elastic/beats/actions/runs/7603570651/job/20705471856?pr=37682

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@efd6 efd6 added Team:Security-External Integrations backport-skip Skip notification from the automated backport with mergify bugfix labels Jan 21, 2024
@efd6 efd6 self-assigned this Jan 21, 2024
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Jan 21, 2024
@elasticmachine
Copy link
Collaborator

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-01-21T22:57:54.020+0000

  • Duration: 151 min 54 sec

Test stats 🧪

Test Results
Failed 0
Passed 28200
Skipped 1866
Total 30066

Steps errors 6

Expand to view the steps failures

filebeat-pythonIntegTest - mage pythonIntegTest
  • Took 47 min 27 sec . View more details here
  • Description: mage pythonIntegTest
auditbeat-packaging-linux - mage package
  • Took 7 min 18 sec . View more details here
  • Description: mage package
heartbeat-packaging-linux - mage package
  • Took 13 min 12 sec . View more details here
  • Description: mage package
metricbeat-packaging-linux - mage package
  • Took 12 min 57 sec . View more details here
  • Description: mage package
packetbeat-packaging-linux - mage package
  • Took 10 min 4 sec . View more details here
  • Description: mage package
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine
Copy link
Collaborator

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 151 min 39 sec

Pipeline error 1

This error is likely related to the pipeline itself. Click here
and then you will see the error (either incorrect syntax or an invalid configuration).

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

The change in 7494535 did not update these requirements, resulting in
inconsistent requirements and doc check failure:

ERROR: Cannot install protobuf==3.19.4 and protobuf==3.19.5 because these package versions have conflicting dependencies.
@elasticmachine
Copy link
Collaborator

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-01-23T20:23:02.907+0000

  • Duration: 152 min 41 sec

Test stats 🧪

Test Results
Failed 0
Passed 28200
Skipped 1866
Total 30066

Steps errors 9

Expand to view the steps failures

auditbeat-packaging-linux - mage package
  • Took 7 min 19 sec . View more details here
  • Description: mage package
auditbeat-packaging-arm-ubuntu-2204-aarch64 - mage package
  • Took 3 min 7 sec . View more details here
  • Description: mage package
heartbeat-packaging-linux - mage package
  • Took 13 min 36 sec . View more details here
  • Description: mage package
heartbeat-packaging-arm-ubuntu-2204-aarch64 - mage package
  • Took 8 min 45 sec . View more details here
  • Description: mage package
metricbeat-packaging-linux - mage package
  • Took 12 min 31 sec . View more details here
  • Description: mage package
metricbeat-packaging-arm-ubuntu-2204-aarch64 - mage package
  • Took 6 min 59 sec . View more details here
  • Description: mage package
packetbeat-packaging-linux - mage package
  • Took 10 min 49 sec . View more details here
  • Description: mage package
packetbeat-packaging-arm-ubuntu-2204-aarch64 - mage package
  • Took 4 min 31 sec . View more details here
  • Description: mage package
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@efd6
Copy link
Contributor Author

efd6 commented Jan 24, 2024

/test

@elasticmachine
Copy link
Collaborator

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 31 min 34 sec

Pipeline error 1

This error is likely related to the pipeline itself. Click here
and then you will see the error (either incorrect syntax or an invalid configuration).

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@efd6
Copy link
Contributor Author

efd6 commented Jan 24, 2024

Abandoned for #37711.

@efd6 efd6 closed this Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify bugfix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants